| ||||||||||||||||||
| |||||||||||||||||||
 |
|
|
| Read this before any use of these guidelines | Contents | |
|
These guidelines contain information and instructions for the GEM hardware used in TSP 4. Note, TSP 4 software shall not be used on old hardware.
If TSP 3 software and hardware is used, please refer to the guidelines for TSP 3. Or, if Carmencita hardware is used, please refer to the official document 1/1532-APZ 302 02/1 and 2/1532-APZ 302/1 (H-Module). These guidelines should not be regarded as official Ericsson documentation, since they are written mainly for my own use. However, if they suit your needs, feel free to use them. Of course, you should always use the official TelORB O&M documentation, but if you get stuck, these guidelines might come in handy. Keep in mind that these guidelines, as well as some of the linked pages below, reflect the UAB environment and that these guidelines are continuously being updated on a daily basis. Disclaimer
I do not take any responsibility for erroneous handling of a TelORB system as the result of following these guidelines. Your feedback and suggestions for improving these guidelines are very much appreciated; send an e-mail to Andreas Johansson. No alcohol was consumed during the writing of these guidelines. 
|
| Contents | Top | |
|
|
|
| General TSP 4 and GEM information |
|
Some general information about TSP 4 is described in this chapter. |
| General information about the hardware in TSP 4 | Contents | |
GeneralThe TSP platform provide the following features:
Five types of processor boards are used in TSP 4, PM, PM-ETH, PM-E1/T1, PMD-ETH and PMDM-ETH. Common of all those boards is All those boards are Two boards called SCB must be present in each magazine. This board contain an ethernet switch The different processors in the systemAll processors in TSP are connected to each other with two (for redundancy ) internal (or traffic) ethernet networks. Five types of processor boards are used in TSP 4, PM, PM-ETH, PM-E1/T1, PMD-ETH and PMDM-ETH. They are used for different tasks, which is described in the following subsectionsTraffic processorsMost of the processors in the system are in the cluster are the traffic processors. They can run the OS Dicos or Linux, depending on what the user want. Still, two of the processors must always run Dicos. All those processors has quite a lot of memory (RAM) but they do not have any hard disk, or the hard disk is disabled. -->More information to come! |
| Delta information between the hardware in TSP 3 and TSP 4 | Contents | |
GeneralThis section is describing the major different between the hardware in TSP 3 and TSP 4.Delta information
|
| Micro configuration | Contents | |
A micro configuration.
GeneralA micro configuration is housed in one cabinet and has 10 processors. It should primarily be used for evaluation, lab trials and demos. The system is not prepared for expansion.In the software distribution for TSP 4 are some template files included, which suggest a "standard" configuration of a micro system, see Proposal of internal network configuration. Various data for the micro system
Hardware configurationA micro configuration in TSP 4 is housed in one cabinet even if only one magazine is present. A micro configuration consists of the following: |
| Mini configuration | Contents | |
A mini configuration.
GeneralA mini configuration is housed in one cabinet and has 21 processors.In the software distribution for TSP 4 are some template files included, which suggest a "standard" configuration of a mini system, see Proposal of internal network configuration. Various data for the mini system
Hardware configurationA mini configuration in TSP 4 is housed in one cabinet. Four magazines are used even if only three contains processor modules. A mini configuration consists of the following:
|
| Midi configuration | Contents | |
A midi configuration.
GeneralA midi configuration is housed in one cabinet and has 31 processors.In the software distribution for TSP 4 are some template files included, which suggest a "standard" configuration of a midi system, see Proposal of internal network configuration. Various data for the midi system
Hardware configurationFour magazines are used in a midi configuration. They are is housed in one cabinet and consists of the following:
|
| Maxi configuration | Contents | |
A maxi configuration.
GeneralThe maxi configuration is the largest TSP 4 system, it is housed in two cabinets and has 42 processors.In the software distribution for TSP 4 are some template files included, which suggest a "standard" configuration of a maxi system, see Proposal of internal network configuration. Various data for the maxi system
Hardware configurationA maxi configuration in TSP 4 is housed in two cabinets. Eight magazines are used even if only five contains processor modules. A maxi configuration consists of the following:
|
| Description of all units |
|
This chapter is describing all units inside the system in alphabetical order. |
| Alarm Panel | Contents | |
GeneralFront view of the alarm panel. The alarm panel is used to give a light and acoustic indication of the alarm status in the system. It is showing how many alarms (1, 2, 3 or more) for each one of the alarm categories (Critical, Major and Minor). The alarm panel, which is not mandatory to have, has the dimensions 832*302*50 (W*H*D) and is intended for wall mounting. The program AlarmPanel in one of the PLGLs in the cluster is sending the same alarm information to both IOs with a short time difference (0.2 s). The IOs receives the information from the internal networks in TCP/IP format, the program AlarmBridge is translating it into serial format and forward it to the serial port on the IOs. The alarm panel is receiving the first alarm information and updates the lamps/buzzer. When alarm panel receives the second alarm information it recognize it is the same information already shown, so nothing happens. The OS is sending alarm information when the alarm panel should be updated with new alarms or when an alarm is cleared. It also sends alarm information every 60 seconds with the same information as was send the last time, i.e. the alarm panel is unchanged. The reason is because the alarm panel will start flashing with all yellow Major lamps if no alarm information have been received for two minutes. If no information have been received for an other six minutes (eight minutes in total) are all red Critical lamps (and the "ATT" lamp) flashing and the buzzer sound (if the buzzer bottom is turned on). No lamp test button exist on the alarm panel. Instead are all lamps turned on for approximately 1 second each time the alarm panel is updated. This is to see that all lamps are working as well as inform the O&M personnel in a more clearly way that something has happen with the alarm situation. ConnectionsAll connectors are located at the bottom part of the alarm panel behind the front panel.The alarm panel is connected to the system via two serial cables to both IO processors. The serial interfaces on the alarm panel are using RS485 standard while the IO processors are using RS 232. That is the reason why each cable consists of two cables with a "converter box" in the middle. The "converter box" is translating between the two serial communication standards. Interface "RS 485 pri" on the alarm panel can be connected to the serial port on any of the IOs. Interface "RS 485 sec" should be connected to the other IO. The power connector "POWER -48V" shall be connected to a -48V source. No redundancy is used for the power. Also see the section Cabling. BuzzerWhen the first indication of an alarm is showed on the alarm panel a buzzer is sounding a short while. All alarm indications has to be gone and a new indication has to be showed before the buzzer sounds again.The buzzer can be switched on and off. The button is located at the bottom part of the alarm panel, just to the left of the connectors, behind the front panel. The buzzer is on when the button is in its leftmost position. ButtonsSee section Buzzer above.LampsLook at the picture in section General, and I hope you understand which lamps indicating what.Software and dataSoftware in IOsThe AlarmBridge LM (LM/D207) should be located and running on the IOs, even if no alarm panel is present in the system. This is taken care of by the IO program package "tools.tar". Look in the directory "/opt/telorb/codearchive/Unix_IDP/included/LM_D207-AlarmBridge" on the IOs for more information.Software in Dicos OSThe AlarmPanel LM (LM/D200) is subscribing on the alarms in the system and sending alarm information to both IOs. This LM is included in the system if the IDP/D22 (GemScbSupervision_IDP) is included in the epct files.Data in Dicos OSThe environment parameter "AlarmPanelAddress" must be included in the epct file(s). This parameter is pointing on the IOs over both internal networks. The port number can also be included if and other port than the default port 5500 should be used.ExamplesHow to include the IDP (in epct):SOFTWARE IDP/D22; // GemScbSupervision_IDP
Parameter without port number (in epct):
Parameter with port number (in epct): NotesHere are some miscellaneous information mentioned.The "ATT" lampThe "ATT" lamp is not used in TSP 4. But the lamp will flash together with all Critical lamps, when the OS has not updated the alarm panel for eight minutes.Use the serial port on the IOs for something elseThe serial port on the IOs are used to communicate with the alarm panel. If the port is needed for something else (e.g. trouble shooting) it is just to remove the cable to the alarm panel, no data has to be changed or any programs has to be stopped. E.g. use the program "minicom" to connect to any processor.When ready, insert the alarm panel cable again. No indication if connection failureNo indication exist inside the IOs or the OS in the cluster if one or both of the connections are lost. The reason is because the alarm panel is quite, it does not send anything back to the IOs. If both connections are lost, some of the lamps on the alarm panel are flashing.Cable lengthThe maximum length of the cable between the IO processors and the converter box is 10 meters and the cable between the converter box and the alarm panel can be maximum 500 meters.Legacy from AXEThis alarm panel is "stolen" from the AXE, it is just the front panel that is changed. That is one of the reason why not RS 232 is used the whole way between the IOs and the alarm panel. |
| Cabinets | Contents | |
GeneralA base cabinet in a maxi configuration.(Click on the picture to enlarge)  
One or two, for the maxi configuration, Ericsson standard BYB 501 cabinets is used in TSP 4. A cabinet has the dimensions 1800 x 600 x 400 mm (H x W x D). Up to four GEM magazines can be housed in a cabinet. The doors are lockable and the cabinet can be equipped with an earthquake protection.
To see a picture of an extension cabinet in a maxi configuration, press extension cabinet. |
| Cable Shelf | Contents | |
GeneralA small and a large cable shelf. Five cable shelves of two different sizes are included in each cabinet. Both types of shelves are identical except that one is 25 mm high while the other is 50 mm. Below each magazine is a small cable shelf located, except the magazine containing the patch panel. There are two 50 mm shelves located, one on the top and one at the bottom of the magazine. NotesIt can be difficult to remove a board because of the cables running in to a cable shelf, see section Remove and insert boards. |
| Fan | Contents | |
GeneralFront view of the fan. (Click the picture to enlarge.)
The main task of the fans is to cool the system. Serial cooling is used, i.e. the air is sucked into the system at the bottom of the cabinet, passing all equipment before it is blown out at the top. Above each magazine is a fan located which is forcing the air upwards in the cabinet. Four fans are present in all cabinets of all types of TSP 4 configurations, except for the cabinet used in a Micro configuration where only one fan is used. All fans are also monitoring the hardware and temperature inside the fan unit. If necessary, the fan is generating an alarm to the left SCB in the magazine below the fan, the SCB is then reporting the alarms to the Dicos OS via SNMP over both internal networks. See Alarms below. Three fans are located inside a fan unit. The speed of the fans depends on the air temperature passing the unit, i.e. an increasing temperature makes the speed on the fans to increase. If a problem occur on one or more of them, an alarm is raised. ConnectionsA fan is powered with -48V from two sources, "Power A -48V" and "Power B -48V". If one of the powers is failing, the fan still fully functioning and an alarm is raised. The connector "Supervision" is used to connect the fan with the left SCB in the magazine below (port "V24"). This V24-connection is used to report alarms from the fan to the SCB. See Alarms below. Also see the section Cabling. AlarmsSome alarms can be generated from each fan, sent to the SCB for further distribution to the Dicos OS via SNMP. To be able to know which fan that is generating an alarm, the name of the reporting SCB is included in the alarm data. Here are all alarms that a fan can generate:
ExampleHere is an example how an fan alarm will look like in the "TelORB Alarms & Notification" window (part of the TelORB Manager):Alarm Type Equipment Object Type ExternalHW Instance SCB_2A Fault Id 27 Severity Major Trend No Change Probable Cause Fan unit 1 : Power branch B (-48) failure Acknowledged Time 2002-5-16 12.55:21 Software and dataSoftware in Dicos OSThe GemScbSupervision LM (LM/D83) is polling all SCBs for HW alarms of which the fan alarms are included. This LM is included in the system if the IDP/D22 (GemScbSupervision_IDP) is included in the epct files.Data in Dicos OSThe environment parameter "GEM_SCB_ADDRESSES" is telling the software the names of all SCBs included in the system. The environment parameter "GEM_SCB_FANUNITS" indicates how many fans (maximum 1 in TSP 4) that are connected to each SCB defined in the parameter "GEM_SCB_ADDRESSES".ExamplesExample of how to include the IDP (in epct):SOFTWARE IDP/D22; // GemScbSupervision_IDP
Example of the parameter settings including eight SCBs (four magazines) where all SCBs called SCB_XA are monitoring a fan (in epct): NotesHere are some miscellaneous information mentioned.The "MIA" lampThe "MIA" lamp is not used in TSP 4, also see section Lamps.No fan supervision redundancyThe supervision of each fan is not duplicated.In my opinion is that not a large concern because the most important fan supervision is the monitoring of the temperature. If one fan supervision is failing, the temperature will still be supervised in the three other fans in the cabinet. The only concern may be if the highest fan supervision is failing where it is possible to have an increase of the temperature in the highest magazine without be able to recognize the high temperature. But, because the cabinet has serial cooling I think he system will work as normal during normal room temperature, even if one fan is stopped. The connection "Supervision extension"The connector "Supervision extension" is not used in TSP 4. It can used if more fans are monitored by one SCB. If that will be the case shall the connector "Supervision extension" on the first fan be connected to the connector "Supervision" on the second fan and so on up to maximum eight fans.Not used alarmIt exist a fan related alarm which is not used in TSP 4. The alarm can maybe be used in the future if each SCB will monitor more than one fan. The alarm look like:
|
| Filter (still TSP 3 information) | Contents | |
GeneralThis filter is a combined air filter and a filter that is stopping hot material to fall down from the cabinet in case of a fire. It should be removed and cleaned with regular intervals. |
| GESB, Gigabit Ethernet Switch Board | Contents | |
General
GESB is an abbreviation for Gigabit Ethernet Switch Board. This board was developed because it was needed in TSP, so no other Ericsson product is using it. The GESBs are connecting all magazines to each other, so all processors in all magazines can reach each other via redundant ethernet communication. All magazines are connected to two GESBs via cables between the SCBs in the magazines and the GESBs. Two GESBs are needed because two internal ethernet networks (A and B) exist in a TSP 4 system. See the overview picture above as well as subsection Connections. Two GESBs are used in Mini, Midi and Maxi configurations while no GESBs are needed in a Micro configuration because it exist of one magazine only. As described in section Magazine and SCB are both ethernet networks inside all magazines running on 100Mb/s. All ethernet communication between the SCBs in the magazines and the GESBs are running on 1Gb/s. So a GESB is basically a ethernet switch with eight ("0" to "7") 1 Gb/s ports at the front of the board. It also exist a CPU on the board. The power is received from the backplane, dual -48V sources. Power supplies on the board is feeding the units with power. Read more about the different units on the GESB in subsection GESB hardware information. The CPU must have two IP addresses, to internal network A and B, to be able to communicate with other units in the system. This addresses are distributed to the CPU, from the IOs, depending on the physical position of the GESB. To see more information about how the GESB is receiving the IP addresses, please read section IP addresses in the system. The programs running on the CPU can, if necessary, be automatically updated from the IOs when the GESB is restarting. Read more about how to update software on the CPU in section Update GESB and SCB software. The CPU is monitoring the ethernet switch and will inform the Dicos OS, via SNMP over both internal networks, if a link to any of the connected SCBs is down. The Dicos OS will then generate an alarm, see subsection Alarms. It is possible to connect to the CPU via telnet and monitor the ethernet switch and the CPU, see Manually monitor the GESB. ConnectionsOne GESB is connecting one of the ethernet networks inside all magazines to each other, building up one internal network (A or B). The other GESB is building up the other internal network. This connection is done by cables between the GESBs and the SCBs in the magazines according to the table below:It does not exist any GESBs in a Micro configuration because it consist of only one magazine so it is not necessary to connect any magazines to each other. Four magazines are present in Mini and Midi configurations. In those configurations are port "0" up to "3" used, while port "4" to "7" is leaved empty. In a Maxi configuration are all ports ("0" to "7") used because eight magazines are present. Also see the section Cabling.
AlarmsThe CPU on board of the GESB can generate the following alarm, which is sent to the Dicos OS via SNMP.
The following alarms, which are involved in the GESB supervision, can be generated by the Dicos OS:
ExampleHere is an example how the link alarm will look like in the "TelORB Alarms & Notification" window (part of the TelORB Manager):Alarm Type Equipment Object Type GEM-HW Instance GESB_A Fault Id 4 Severity Major Trend No Change Probable Cause Link GESB-SCB [2] is down Acknowledged Time 2002-6-10 10:26:26 Software and dataSoftware in Dicos OSThe GemHwScanner LM (LM/D176) is polling both GESBs for link alarms. This LM is included in the system if the IDP/D22 (GemScbSupervision_IDP) is included in the epct files. Some more unofficial information about the GemHwScanner LM can be found here.Software in the GESBThe software executed on the GESBs are also stored on the IOs and will be transferred (if necessary) to the GESBs during start up. The set up of transferring the software on the IOs is taken care of by the IO program package "tools.tar".Here is a list of all software and a short description what it does.
Data in Dicos OSThe environment parameter "GESB0" and "GESB1" are telling the software the names of the GESBs in the system. They also tell in which magazine and slot they are located. The last information is how many SCBs that are connected to each GESB.The Dicos OS knows the name of the GESBs from the parameter above but it will use two (one for each internal network) IP addresses to communicate with the GESB. To translate the name to IP addresses the DNS table in Dicos is used. To include the GESBs in the DNS table two initial data parameters are used, namely "SymbolicAddress_XX" and "NumericAddress_XX". Data in IOsThe parameters "internal-network gesba_0", "internal-network gesba_1", "internal-network gesbb_0" and "internal-network gesbb_1" in the file "telorb.conf" is informing the dhcp function on the IOs which IP addresses that should be distributed to the GESBs.ExamplesHow to include the IDP (in epct):SOFTWARE IDP/D22; // GemScbSupervision_IDP
Parameter settings including both GESBs into the system (in epct):
Parameter settings to insert the GESB names into the DNS table (in epct):
Parameter settings to give the GESBs their IP addresses (in telorb.conf): Manually monitor the GESBIt is possible to monitor the GESBs. Telnet is used to log in to the board. A command line interface is used to monitor the CPU, ethernet ports to the internal networks etc.At the moment is it not possible to print data and statistics about the eight 1Gb ports. This feature will be introduced later on. A user id and a password for the GESB must be known before it is possible to log on. Login to the GESBLogin to the GESB like this: "razor" "assar"
Some useful commandsHere are some useful commands mentioned and explained.
Port numbering in the GESBWhen it is possible to print data and statistics about the 1Gb ports, I will add information here how to print it.Printout descriptionWhen it is possible to print data and statistics about the 1Gb ports, I will add an example here, explain the printout.GESB hardware informationIn this subsection are the units on the GESB described in a little bit more detail.Block diagram over the GESB.
CPUThe CPU is an embedded processor, MPC860P, from Motorola. It is running on 80 MHz and has 8 MB Flash memory and 16 MB RAM.The CPU is connected to the ethernet switch via a PCI bus. With software (telnet and SNMP-Agent) on the CPU is it possible to do the following on the switch:
A temperature sensor, mounted on the most warm position on the ethernet switch, is connected to the CPU. If the temperature increase to 80 °C will the CPU order a power reset. The GESB will be hold in a reset state until the temperature falls below 75 °C. The CPU has two ethernet ports (eth0 and eth1) which are connected to the backplane. The speed is 10 Mbit/s, not 100. During start up is the CPU reading the address plugs as well as the slot address. This information is used when the CPU will ask the IOs for IP addresses to both ethernet ports. The JTAG interface on the backplane is connected to programming interface on the left side of the magazine, see section Magazine. It is used on the factory to load the SW on the flash memory. Read more about this in section Update GESB and SCB software. Ethernet SwitchThe ethernet switch is build on a chipset from Broadcom Corporation and has the following features:
Hardware InventoryInformation yet to come.Power SupplyThe power to the GESB is received from the back plane. The two -48V sources are put together by diodes before it is transferred to two DC/DC converters. One converter is generating 3.3V and 2.5V, while the other converter is generating 1.8V. 1.2V and 1.4V is generated from 1.8V and 2.5V respectively. These voltages are distributed to all units on the board.The total power dissipation from the GESB is 30W. Voltage SupervisionThe voltage supervision will monitor 3.3V, 2.5V, 1.8V and 1.2V. If any of the voltages drop below a threshold is a power reset signal sent to all logics on the board, which will restart.NotesHere are some miscellaneous information mentioned.The "MIA" lampThe "MIA" lamp is not used in TSP 4, also see section Lamps.No null modem cables any moreAll ports on the GESB are automatically recognizing the polarity of the port at the other end of the cable. So, it is not necessary to use any twisted (or null modem) ethernet cables, the board will take care of that.Internal network on wrong sideDue to mistake during the development of the PMs is the first internal network, or network A, build up by the SCBs at the right side of the magazines. The most natural way should be the have internal network A at the left side. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Magazine (still TSP 3 information) | Contents | |
GeneralAn empty GEM unit (magazine).(Click on the picture to enlarge) 
A GEM (Generic Ericsson Magazine) is a magazine developed to be used in a number of products in the Ericsson portfolio, so the GEM is not only used in TSP products.
The magazine has 26 slots (or positions) where slot 0 (leftmost) and slot 25 (rightmost) are reserved for SCBs. Those two slots are 30 millimetres wide. The rest, slot 1 to 24, are used for processor boards and they are 15 wide. The minimum width for a processor in TSP 4 is 30 millimetres, that means that every second slot (even slot numbers) will not be used. Each one of those slots (0 to 25) will receive the following:
The maximum allowed power consumption in one magazine is 800 W. But when four magazines are placed on to of each other and serial cooling is used, the maximum allowed power consumption is approximately 600 W per magazine. For information about the power consumption for the different configurations, see section Micro configuration, Mini configuration, Midi configuration or Maxi configuration. Ethernet buses in the magazine
Power buses in the magazine
Physical addresses in the magazine
Address plugsFour magazines are mounted in a cabinet. The following magazine numbering is used in TSP 3:
Magazine addressingThe address plugs inserted in the address positions has the product number TVJ 119 1111/XX, where the suffix is the number that will be read by the system.Here is an example of with address plugs that can be used in a maximum configured TSP3 system. The node number can be change on different nodes.
NotesA magazine contains of 26 slots. A magazine is also divided into 86 parts horizontally, this physical dividing is shown at the top and bottom of the magazine. The following table is showing on which physical position all slots are located. See also the section Numbering below.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Patch panel (still TSP 3 information) | Contents | |
GeneralFront view of a Patch Panel. 
All external cabling (except power cables) will be connected to/from the system via a patch panel. Magazine 2 in both cabinets are housing a patch panel which is divided into two parts. The lower part is connecting all necessary units inside the system to the patch panel. This cabling is done during the assembling of the cabinet.
All external cables shall be connected to the connectors in the upper part. It is possible to connect 40 cables to each cabinet, see picture. Meaning of the connectorsThe connectors in the patch panel has the following functions:
NotesIt is a straight connection between a connector in the lower part and the same connector in the higher part, i.e. no intelligence or electronics is added on the patch panel board.The "MIA" lamp is not used in TSP 3. |
| PM, Processor Module | Contents | |
|
Information yet to come. |
| PM-ETH, Processor Module with two ethernet ports | Contents | |
|
Information yet to come. |
| PM-E1/T1, Processor Module with four SS7 ports | Contents | |
|
Information yet to come. |
| PM-E1/T1, Processor Module with two 18Gb hard disks and two ethernet ports | Contents | |
|
Information yet to come. |
| PM-E1/T1, Processor Module with two 18Gb hard disks, DVD, Tape and two ethernet ports | Contents | |
|
Information yet to come. |
| SCB, Switch Control Board (still TSP 3 information) | Contents | |
GeneralAn SCBs (Switch Control Board) are located in both ends of each magazine. In TSP 3 those have the following tasks:
Ethernet SwitchAn ethernet switch is housed inside the SCB. Duplicate ethernet buses exist among other things in the backplane of the magazine. The ethernet switch in the SCB at the leftmost position in the magazine is controlling one of those buses, the rightmost the other bus.The ethernet switch has 26 100Mb/s ports towards the backplane. Two of them are used by the both SCBs. So, up to 24 units (processors) can be inserted in the magazine and receive dual ethernet connections. Also one 100Mb/s port and one 1Gb/s port are located at the front of the board. With those ports is it possible to connect the networks in the backplane to the outside world. Due to a misunderstanding during the design phase of the TPs in TSP 3 is the first traffic network (net 1 or net A) controlled by SCBs to the right side of a magazine. For an overview picture of the networks in TSP 3 take a look at the picture Schematic ethernet connection in TSP3. Power SuppliesThe SCB is also responsible for the power distribution inside the magazine. Two -48V power cables are feeding each SCB, they are connected to the connectors "-48V L" and "-48V R" from the same power source.The SCB is filtering the power before it redistribute the -48 V to the backplane via fuses. "-48V L" on both SCBs in a magazine are feeding the left half of the magazine, "-48V R" the right half. The SCB itself is powered from the backplane, i.e. if both power inlets are disconnected, the SCB is still running, feed by the other SCB, and alarms are generated. Ethernet interfacesThe 1Gb/s link, "1000BaseT", is used to connect the SCB to the GESB, see section GESB and Cabling .If the function network redundancy is used the network redundancy links should be connected to the 100 Mb/s link, "100BaseTx", at the front of the SCBs in magazine 2, see section Cabling . The CPU in the SCB has two ethernet interfaces to both internal networks. The port "eth1" is connected to traffic network A (right SCB) while the port "eth0" is connected to traffic network B (left SCB). AlarmsTo be able to have the alarm function to work must the IP addresses be set on the SCB, see section Notes below.All SCBs in the system are collecting and reporting hardware related alarms. All leftmost SCBs are also reporting fan related alarms since they are connected to the fan just above, via the port "V24". The Dicos OS has SNMP contact to all SCBs via both traffic networks by use of a symbolic name, (environment parameter "GEM_SCB_ADDRESSES"). That name is translated into two IP addresses by DNS function inside TelORB. Any names for the SCBs can be used but in our TelORB lab have we used the following names:
The hardware alarms that can be generated are fan and temperature related alarms, see section Fan above, and the two following power alarms:
Monitor the SCBTo be able to monitor the SCB must the IP addresses be set on the board, see section Notes below.Telnet is used log in to the SCB. A command based interface is used to monitor all ethernet ports on the board. See section Monitor SCB / GESB below. NotesThe "TEST" connector is not used in TSP 3. In later releases will it be used as a ethernet test channel into the system.The "EXT ALARM" connector is not used in TSP 3. In later releases will it be possible to connect one external alarm per SCB. The SCB is used in the AXE world as well, there are the connectors "RPB-S/x" used but they are not used in TSP 3. The "MIA" lamp is not used in TSP 3. To get the alarm monitoring to work must some environment parameters be specified, see section epct setting for GEM HW below. Because the SCB has a lot of pins to the backplane is it very sluggish to insert and remove the board. To ensure proper connection to the backplane both screws should be tighten firmly. Two IP addresses should be set in all SCBs to have the alarm and monitoring function to work. In TSP 3 it does not exist any way to set those addresses. In future releases will the DHCP function in the SP's together with the physical positions of the SCBs be used to set the IP addresses. It exist a work around to fix this problem in TSP 3, see section Set IP addresses in SCB / GESB below. All ethernet ports (except "TEST") on the SCB are automatically recognizing the polarity of the port at the other end of the cable. So, it is not necessary to use any twisted (or null modem) ethernet cables, the board will take care of that. |
| Various descriptions |
|
In this chapter are some useful notes, information, descriptions and "how to dos" mentioned, which can be handy to know when working with the TSP 4 hardware. |
| Proposal of internal network configuration | Contents | |
GeneralIn TSP 4 will not the internal networks be exposed outside the system. That means that any network addresses can be used, regardless of the surrounding networks.Of course it is up to the customer to decide which network addresses to be used on the internal networks. But, try to force all TSP 4 users to have the same configuration for the internal networks, a number of predefined configuration files are delivered together with the software distribution. The files can be found in the following directories in the distribution: Four configuration files are included for each hardware configuration, two files for zone 1 and two for zone 2. The "telorb.conf" file (e.g. r14_linux_maxi_zone1.telorb.conf.template) is used to set up the configuration in the IOs. The "epct" file (e.g. r14_linux_maxi_zone1.epct.template) is used when building the system. If you have a new system to configure those files are a good starting point. In the subsections below can those configuration files be viewed for each hardware configuration type, they contain a lot of useful comments. Together with the configuration files is it possible to see an overview picture of each cabinets, just click on a specific cabinet. Those overview pictures contains the most useful data defined in the configuration files. A more detail information picture can be seen if a magazine is clicked in the cabinet overview picture. NotesHere are some miscellaneous information mentioned.Take the configuration files from the distributionIf the configuration files are needed do not take them from this page, fetch them instead from your distribution.PrintingThe overview pictures can be handy to print (landscape) on paper and have beside you when working with TSP 4.Empty templateFor those few of you not using the delivered configuration files I have prepared an empty overview picture where you can insert your values.Explanation of the overview pictures of the cabinetsThe following data will be showed in the overview pictures of the cabinets. See Explanation of the detail pictures of the magazines for more details of the values.In the leftmost part of each magazine are the address plug positions located. The four positions has the following meaning:
Each processor unit can have 11 information lines, which have the following meanings:
Explanation of the detail pictures of the magazinesThe following data will be showed in the detail pictures of the magazines.
Micro configurationBelow are zone 1 and 2 in a micro configuration showed together with the related configuration files. Click on the files to read them or click on a cabinet to see an overview picture of the cabinet. This picture is showing some useful data of the system, which can be handy to know when working with a micro system which is configured with the delivered configuration files.To see even more information about the system, click on any magazine in the overview picture.
Mini configurationBelow are zone 1 and 2 in a mini configuration showed together with the related configuration files. Click on the files to read them or click on a cabinet to see an overview picture of the cabinet. This picture is showing some useful data of the system, which can be handy to know when working with a mini system which is configured with the delivered configuration files.To see even more information about the system, click on any magazine in the overview picture.
Midi configurationBelow are zone 1 and 2 in a midi configuration showed together with the related configuration files. Click on the files to read them or click on a cabinet to see an overview picture of the cabinet. This picture is showing some useful data of the system, which can be handy to know when working with a midi system which is configured with the delivered configuration files.To see even more information about the system, click on any magazine in the overview picture.
Maxi configurationBelow are zone 1 and 2 in a maxi configuration showed together with the related configuration files. Click on the files to read them or click on one of the four cabinets to see an overview picture of that cabinet. This picture is showing some useful data of the cabinet, which can be handy to know when working with a maxi system which is configured with the delivered configuration files.To see even more information about the system, click on any magazine in the overview picture.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Hardware Inventory | Contents | |
| Information yet to come ! |
| Not possible to reach (ping) GESB or SCB | Contents | |
GeneralI have heard that some TSP 4 users have had problems to reach (ping) the GESBs and SCBs in their systems. In nearly all cases have the problem been that the address plugs in the magazines are missing or the wrong plugs have been present. Therefore I wrote this section to try to explain shortly how it works and how to do.In TSP 4 are the GESBs and the SCBs receiving their IP addresses, from the IOs, depending on address plugs as well as their physical positions. So, it is necessary to have correct address plugs inserted in the magazines and to have the GESBs and SCBs in right positions in the magazine. Otherwise will never the GESBs and SCBs get any IP addresses. Read more about how IP address are distributed in a TSP 4 system in section IP addresses in the system. Address plugs in the magazinesAt the left side of each magazine it exist four address plug positions. They are called from the top to the bottom, "Address Plug 0 (AP_0)", "Address Plug 1 (AP_1)", "Address Plug 2 (AP_2)" and "Address Plug 3 (AP_3)". Address plugs can be inserted in AP_0, AP_1 and AP_3. Never insert a address plug in AP_2. AP_2 is used as a programming interface mostly used at the factory.16 different address plugs can be used. They are called ROJ 119 1116/XX, where XX can be 00, 01 up to 15. To read more about the address plugs see subsection address plugs in section magazine. In TSP 4 is it not possible to choose which address plugs to use, it must be the ones specified below.
Position of the GESBs and SCBs in the magazinesEach magazine has 26 slots (0 to 25) where boards can be inserted, see section Magazine.The slot most to the left (slot 0) and the slot most to the right (slot 25) are reserved for SCBs. The rest, slot 1 to 24, can be used for any type of board. If the system consists of more than one magazine must two GESBs be used, otherwise it does not exist any GESBs in the system. In TSP 4 must the GESBs and SCBs be located in the following magazines and positions.
NotesHere are some miscellaneous information mentioned.Two or more systems in one cabinetSometimes, in labs, two or more small TSP 4 systems can be located in the same cabinet. All these systems shall have their magazine numbering starting with zero. For example two Micro systems can be located in one cabinet. Both those magazines shall have number zero. But if they are connected to each other with two GESBs, building up a larger system, should the magazine numbering change to magazine zero and one.Use of other slots or address plugsThe SCBs must be located in slot 0 and 25 in each magazine while the GESBs can be inserted in any position, still doing their main tasks. It is not possible for the IOs to distribute the IP addresses to the GESBs and SCBs in the following circumstances:
The main functions (power supply and ethernet switches) in the GESBs and SCBs will work without IP addresses but it is not possible for the Dicos OS to reach the boards, so the hardware alarm and hardware inventory functions will fail. Read more about the alarm function in sections GESB and SCB, inventory function in section Hardware Inventory. Read changed address plugsThe address plugs are scanned during start up of GESB and SCB. If any address plug is changed/added/removed must the GESBs and SCBs in that magazine be restarted.No address plugs in AP_2AP_2 (third from the top) is a programming interface towards boards inserted in the magazine. It is mostly used at the factory.No address plugs should be inserted in this position because old revisions of the magazine could be damaged if some of the address plugs was inserted. This problem is corrected in all magazines delivered in TSP 4. But, no address plugs should be inserted anyhow. |
| Remove and insert boards | Contents | |
GeneralNo space exist between a magazine and the cable shelve(s) just over or below the magazine. So, when a board should be removed from the magazine it is not enough to disconnect the cables to that board. All disconnected cables are running into the cable shelf in front of the board. Because lack of space it is impossible to bent those cables so they are not in the way when the board is removed. Instead is it necessary to open the cable shelf and remove those cables. An easier way exist if not so many cables, press the cable shelf hard away from the magazine.Be sure that the boards next to a board that will be removed is screwed to the magazine. Otherwise can the neighbour board(s) be pulled out as well because it is so tight between boards in the GEM. To ensure proper function should all boards be screwed tight to the magazine, especially the SCB. |
| Contacts (still TSP 3 information) | Contents | |
GeneralTo ensure a safety EMC protection all connectors shall be of the Concept type (or Sofix type). Today, most the connectors are of that type but some are of the type RJ45 and USB. Those will be changed to Concept connectors in later releases. It also exists D-sub connectors, those will not be changed to Concept because they are only used for test and fault finding purposes. |
| Lamps | Contents | |
GeneralDue to Ericsson standard no other lamps than the "MIA" (Manual Intervention Allowed) should be visible on the front of a board. The idea is that the "MIA" lamp should be on when the board needs to be changed. The lamp can still be controlled if the power on the board fails. All other lamps could confuse the personnel.Anyhow, due to production circumstances more lamps are visible on the processor modules. |
| Power to the system | Contents | |
GeneralAll power distribution inside the system is described in the section SCB above. How the power is coming in to the system is described here.A cabinet consists of four magazines with a fan just above each magazine. A magazine/fan is feed with -48V from both ends. One -48V power cable is connected to the power distribution in the building. The other end is split into three connectors. Two of these connectors are mounted to one SCB, the third is connected to the fan. A second cable is connected in the same way but to the other side of the magazine/fan. A ground cable to each cabinet is also necessary to connect. The alarm panel need one -48V connection. So two -48V power cables are needed for each magazine. That will be eight cables per cabinet. In our TelORB lab we have been using four cables and it was no problem at all. 16A fuses shall be used. |
| Cabling (still TSP 3 information) | Contents | |
|
Picture of the cabling for a maximum TSP 3 system.
(Click on the picture to enlarge) 
GeneralHave a look at the picture to get an overview for the cabling in TSP 3.All cables which are connecting units inside the system to each other, are connected directly between the units. The power cables are connected directly to the power distribution. The rest of the cables are connected via the Patch panel, which is not showed in the picture. NoteOn the SCBs and Patch panel it is possible to connect cables for external alarms. External alarms is not included in TSP 3, so no cable are needed on those positions. |
| Physical numbering | Contents | |
GeneralPhysical position numbering in TSP 4.(Click on the picture to enlarge) 
To be able to find a physical position in a GEM system, the following three position numbering are used.
As an example, a label with a position can look as follow:
The position information has the following meaning:
Slot position vs. physical positionAs showed in the picture a magazine contain 26 slots, each one is connected to dual ethernet connections, dual power connection and a O&M connection, see section Magazine. The following table is showing on which physical position all slots are located.
NotesDue to the fact that the minimum width for a processor is 30 millimetres and the width of one slot is 15 millimetres, are all slots with even number not used in TSP 4. |
| Product numbers and useful documentation | Contents | |
GeneralI have tried to include most of the necessary and useful things to know about the hardware used in TSP 4 in these guidelines. A lot more information can be found in the official documentation for the different hardware products.In the list below are the most essential hardware products showed in a product structure layout. All product numbers are showed, which makes is easier to search for more information about the product. Some useful document numbers are also included in the list. NotesHere are some miscellaneous information mentioned.Old information in the sectionProducts can change over a period of time and I will not check, on a regular basis, that the contents in the list below are up to date. So it can happen that the information below is not accurate.Viewing official documents mentioned in the sectionI have links in the list to, what I think, good documents, describing the products. At the moment it is not possible to view the document when clicking on such link. I hope it will be possible in the future. So, at the moment it is necessary to open the documents yourself. It exist some ways to look at documents in Ericsson archives, here is a short explanation how to use "Elipse" via a web interface.
* Document numbers where 1075 is included in the prefix is a document used when the cable labels are printed. It can be useful when it is necessary to know where a cable should be connected. See this for a description how the 1075-documents is interpreted.
List of the product numbers and some good documents
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Software revisions | Contents | |
GeneralThis section is showing the revisions for all hardware related software in the different TSP 4 releases.List of software revisions
|
| IP addresses in the system (still TSP 3 information) | Contents | |
GeneralTo be able to have the hardware alarm function and the monitoring (of SCB and GESB) functions to work must all SCBs and GESBs have two IP addresses, one for each internal network.In TSP 3 it does not exist any function to distribute those addresses. In future releases will the DHCP function in the SP's together with the physical positions of the SCBs and GESBs be used to set the IP addresses. Here is a procedure to manually solve this problem. This solution is nearly the same that will be used in future releases but then is the data set up automatically. How to doHere is an explanation how to make the DHCP function to distribute the IP addresses to the SCBs and GESBs depending on their physical position.
NotesThe file "/opt/telorb/etc/dhcpd.pxe.conf" is overwritten when the script "opt/telorb/codearchive/iom_scripts/configureTelORB.sh" is run. When this script is run must the above mentioned procedure be done again.Two address plugs has to be inserted in each magazine to have the "position to IP address" function to work. Those should be in address position 1 and 3, see section Magazine above and the explanation below. Here is an explanation of the position identifier used by the DHCP function. "0.1.255.0:eth0.1" (DHCP identifier) !---- eth1.1 is the ethernet port to internal network A eth0.1 is the ethernet port to internal network B !-------- Position in the magazine. 0 is the position for the left SCB 25 is the position for the right SCB 23 is the position for the GESBs !----------- The value of the address plug in address position 0 (highest) in the magazine. If no address plug is used is the value 255 !-------------- Magazine number (0 to 4). This is the value of the address plug in position 1 (third from bottom) !---------------- Node number. This is the value of the address plug in position 3 (lowest) ExampleHere is the complete configuration data for SCB and GESB IP set up in a fully equipped TSP 3 system.Not used magazines and equipment can be removed before this data is inserted in your system. Of course must the IP addresses be changed so it mach your system. When copying from the example below, do not forget the last parenthesis.
*****EXAMPLE********************************************************************
Group {
#Set the time the SCB/GESB shall remember the IP address to infinite
default-lease-time = ff:ff:ff:ff;
max-lease-time = ff:ff:ff:ff;
filename = "";
########## Magazine 0 (lowest in base cabinet) ###################
########## SCB_0A (Left SCB) ##########
##### Eth to net A ######
host SCB_0A_netA {
option dhcp-client-identifier = concat(00,"0.0.255.0:eth1.1");
fixed-address 134.138.76.10;
}
##### Eth to net B ######
host SCB_0A_netB {
option dhcp-client-identifier = concat(00,"0.0.255.0:eth0.1");
fixed-address 134.138.77.10;
}
########## SCB_0B (Right SCB) ##########
##### Eth to net A ######
host SCB_0B_netA {
option dhcp-client-identifier = concat(00,"0.0.255.25:eth1.1");
fixed-address 134.138.76.11;
}
##### Eth to net B ######
host SCB_0B_netB {
option dhcp-client-identifier = concat(00,"0.0.255.25:eth0.1");
fixed-address 134.138.77.11;
}
########## Magazine 1 (second from bottom in base cabinet) ##########
########## SCB_1A (Left SCB) ##########
##### Eth to net A ######
host SCB_1A_netA {
option dhcp-client-identifier = concat(00,"0.1.255.0:eth1.1");
fixed-address 134.138.76.12;
}
##### Eth to net B ######
host SCB_1A_netB {
option dhcp-client-identifier = concat(00,"0.1.255.0:eth0.1");
fixed-address 134.138.77.12;
}
########## SCB_1B (Right SCB) ##########
##### Eth to net A ######
host SCB_1B_netA {
option dhcp-client-identifier = concat(00,"0.1.255.25:eth1.1");
fixed-address 134.138.76.13;
}
##### Eth to net B ######
host SCB_1B_netB {
option dhcp-client-identifier = concat(00,"0.1.255.25:eth0.1");
fixed-address 134.138.77.13;
}
########## Magazine 2 (third from bottom in base cabinet) ##########
########## SCB_2A (Left SCB) ##########
##### Eth to net A ######
host SCB_2A_netA {
option dhcp-client-identifier = concat(00,"0.2.255.0:eth1.1");
fixed-address 134.138.76.14;
}
##### Eth to net B ######
host SCB_2A_netB {
option dhcp-client-identifier = concat(00,"0.2.255.0:eth0.1");
fixed-address 134.138.77.14;
}
########## SCB_2B (Right SCB) ##########
##### Eth to net A ######
host SCB_2B_netA {
option dhcp-client-identifier = concat(00,"0.2.255.25:eth1.1");
fixed-address 134.138.76.15;
}
##### Eth to net B ######
host SCB_2B_netB {
option dhcp-client-identifier = concat(00,"0.2.255.25:eth0.1");
fixed-address 134.138.77.15;
}
########## GESB_A ##########
##### Eth to net A ######
host GESB_A_netA {
option dhcp-client-identifier = concat(00,"0.2.255.23:eth1.1");
fixed-address 134.138.76.20;
}
##### Eth to net B ######
host GESB_A_netB {
option dhcp-client-identifier = concat(00,"0.2.255.23:eth0.1");
fixed-address 134.138.77.20;
}
########## Magazine 3 (highest in base cabinet) ##########
########## SCB_3A (Left SCB) ##########
# Ethernet interface to internal network A.
host SCB_3A_netA {
option dhcp-client-identifier = concat(00,"0.3.255.0:eth1.1");
fixed-address 134.138.76.16;
}
# Ethernet interface to internal network B.
host SCB_3A_netB {
option dhcp-client-identifier = concat(00,"0.3.255.0:eth0.1");
fixed-address 134.138.77.16;
}
########## SCB_3B (Right SCB) ##########
##### Eth to net A ######
host SCB_3B_netA {
option dhcp-client-identifier = concat(00,"0.3.255.25:eth1.1");
fixed-address 134.138.76.17;
}
##### Eth to net B ######
host SCB_3B_netB {
option dhcp-client-identifier = concat(00,"0.3.255.25:eth0.1");
fixed-address 134.138.77.17;
}
########## GESB_B ##########
##### Eth to net A ######
host GESB_B_netA {
option dhcp-client-identifier = concat(00,"0.3.255.23:eth1.1");
fixed-address 134.138.76.21;
}
##### Eth to net B ######
host GESB_B_netB {
option dhcp-client-identifier = concat(00,"0.3.255.23:eth0.1");
fixed-address 134.138.77.21;
}
########## Magazine 4 (lowest in the extension cabinet) ##########
########## SCB_4A (Left SCB) ##########
##### Eth to net A ######
host SCB_4A_netA {
option dhcp-client-identifier = concat(00,"0.4.255.0:eth1.1");
fixed-address 134.138.76.18;
}
##### Eth to net B ######
host SCB_4A_netB {
option dhcp-client-identifier = concat(00,"0.4.255.0:eth0.1");
fixed-address 134.138.77.18;
}
########## SCB_4B (Right SCB) ##########
##### Eth to net A ######
host SCB_4B_netA {
option dhcp-client-identifier = concat(00,"0.4.255.25:eth1.1");
fixed-address 134.138.76.19;
}
##### Eth to net B ######
host SCB_4B_netB {
option dhcp-client-identifier = concat(00,"0.4.255.25:eth0.1");
fixed-address 134.138.77.19;
}
}
*****END OF EXAMPLE*************************************************************
Old way to set the IP addressesBefore the above mentioned way to set the IP addresses was known the following way have to be used. Maybe this can be used in some lab sites so this information is kept.The following material is needed to set the IP addresses in the SCB and GESB:
Use the following settings:
Before starting, be sure the RPG Debug Terminal is connected to the flat cable and to the serial cable at connector "A". Also start your terminal program. How to do:
NotesIf you type something wrong and get an error result, the prompt is changed to "?>". To reset this so a normal operation is archived do the command:clear error If you want to remove the IP data that has been set according to the above procedure, do the following.
|
| Update software on GESB and SCB | Contents | |
| Information to come ! |
| Monitor GESB and SCB (still TSP 3 information) | Contents | |
GeneralIt is possible to monitor the GESBs and SCBs. Telnet is used to log in to the board. A command based interface is used to check ethernet ports, software units, set parameters etc.Login to the GESB and SCBThe same login procedure is used on the GESB and the SCB. Username and password is set when the software is loaded into the board. "razor" "assar"
Command:
Result: Some useful commandsHere are some useful commands mentioned and explained.
Port numbering in the GESBInformation yet to come !Port numbering in the SCBEach SCB has 26 ports to the backplane and tree ports to the front of the board. The table below is describing which unit that is connected to each port number. The ports 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22 and 24 are not used in TSP 3.To see the status on ethernet port connected to traffic processor 6, login to one of the SCBs in magazine 0 and do the following command:
To see the status on the "1000BaseTx" ethernet port at the front of the SCB, login to that SCBs and do the following command:
Printout descriptionThis is an example of a printout ordered by the command "scbsw -mib -pX". Some notes (#) are added to clarify some output parameters.error : 0 GoodBytesRx: 91614884 GoodBytesTx: 125073636 GoodFramesRx: 1177994 GoodFramesTx: 1401203 TotalBytesRx: 91616344 TotalFramesRx: 1178014 BroadcastFramesRx: 4404 MulticastFramesRx: 0 CRCErrors: 0 OversizedFrames: 0 FragmentsRx: 0 JabberFramesRx: 0 Collisions: 0 LateCollisions: 0 Frames_64: 882655 Frames_65_127: 1561143 Frames_128_255: 126004 Frames_256_511: 1591 Frames_512_1023: 2837 Frames_1024_MAX: 4987 Reserved1: 0 FramesDropped: 0 MulticastFramesTx: 383130 BroadcastFramesTx: 93680 UndersizedFrames: 0 link_state: 1 # 1=up, 0=down link_speed: 1 # 0=10 Mbit/S, 1=100 Mbit/s duplex_mode: 1 flow_control: 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| epct setting for GEM HW (still TSP 3 information) | Contents | |
GeneralThe epct settings needed for the GEM is data for the hardware alarm function. It is data to load the software, also parameters to tell the Dicos OS about the hardware configuration is needed.SoftwareOnly one IDP is necessary to add to the system, namely:
ENVIRONMENT DATAFour parameters are added to inform the system about the HW configuration, those are the following:
INITIAL DATATo translate the name of the SCB into IP addresses are the following parameters used.
ExampleHere is an example used in a system, with 5 magazine, in our lab. When testing the hardware alarm function it is handy to reduce the time between polling to 1 second, "GEM_SCB_POLLINTERVAL = 1000". ENVIRONMENT DATA GEM_SCB_ADDRESSES = "SCB_0A,SCB_0B,SCB_1A,SCB_1B,SCB_2A,SCB_2B,SCB_3A,SCB_3B,SCB_4A,SCB_4B" GEM_SCB_FANUNITS = "1,0,1,0,1,0,1,0,1,0" GEM_SCB_MAXFANS = 1 GEM_SCB_POLLINTERVAL = 15000 ENDDATA INITIAL DATA SymbolicAddress_4 = "SCB_0A" NumericAddress_4 = "134.138.76.10:134.138.77.10" SymbolicAddress_5 = "SCB_0B" NumericAddress_5 = "134.138.76.11:134.138.77.11" SymbolicAddress_6 = "SCB_1A" NumericAddress_6 = "134.138.76.12:134.138.77.12" SymbolicAddress_7 = "SCB_1B" NumericAddress_7 = "134.138.76.13:134.138.77.13" SymbolicAddress_8 = "SCB_2A" NumericAddress_8 = "134.138.76.14:134.138.77.14" SymbolicAddress_9 = "SCB_2B" NumericAddress_9 = "134.138.76.15:134.138.77.15" SymbolicAddress_10 = "SCB_3A" NumericAddress_10 = "134.138.76.16:134.138.77.16" SymbolicAddress_11 = "SCB_3B" NumericAddress_11 = "134.138.76.17:134.138.77.17" SymbolicAddress_12 = "SCB_4A" NumericAddress_12 = "134.138.76.18:134.138.77.18" SymbolicAddress_13 = "SCB_4B" NumericAddress_13 = "134.138.76.19:134.138.77.19" ENDDATA |
| End of the page | Contents | |
on the line of the document you would like to see.
on the line of the document you would like to save.